-
-
Notifications
You must be signed in to change notification settings - Fork 46.6k
Add breadth first search #3632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add breadth first search #3632
Conversation
…rithm with a pathfind visualisation to show the result
Ok I'm sorry I'll leave this here anyway but those first two commits are from a different pull request(#3454). I don't know why the commits from that one are here as well, I made different branches for both. Help would be appreciated. (The failed tests are from those 2 commits, that's a different problem on that other pull request) |
Hello @Rolv-Apneseth, I'm thinking they both ended up counting as commits because you pushed commits from (#3454) earlier, regardless of what branch you are on currently. To get rid of the old branch changes, you have to delete them locally and remotely I believe, or stash them in case you would want to come back to it. Essentially you want to remove your Git changes. Anyway, after this, the old branch commits wouldn't be part of your commits I'm thinking. |
Please run |
I think you can enable the github actions in your setting of the fork too. |
You may open a new branch for those changes, and file a new PR. When you've done, you can close this PR. |
@popyea I did open a new branch for these changes just I don't know very well how branches work. I will try to file a new pr. @kadhirash thank you I will try that |
Added a .py file in the searches folder for breadth-first search algorithm with a pathfind visualisation to show the result.
Included doctests and have already run black, mypy and doctests locally.
In relation to #3260